2015-09-04 - 19936 - Spec - Vendor Capacity Planning #ABAPVendorCapacity #MMPPSupport
SPECIFICATIONS
19936 - Spec - Vendor Capacity Planning
Purpose
Implementation of Vendor Capacity Planning.
Admin Info
| Purpose |
Implementation of Vendor Capacity Planning |
| Requested By |
Jeffrey Mau/ Babu Lankipalli |
| Spec Created By |
Laxman |
| Spec Created Date |
09/07/2015 |
| Spec QA by |
Laxman |
| Objects |
|
| Document Status |
Complete |
Estimates
| Sl.No |
Activity |
Estimation in Hours |
| 1 |
Research |
32 |
| 2 |
Documentation |
24 |
| 3 |
Development/ Config |
268 |
| 4 |
Unit test in DEV |
32 |
| 5 |
Unit test in QUA |
24 |
| 6 |
Other activity |
|
| TOTAL |
380 |
| BluePrint |
Realization DEV (incl. unit Test) |
Int. Testing Q |
Cutover /Go-Live |
Total |
|
| Calendar Days --> |
7 |
25 |
3 |
15 |
50 |
| Hours |
|||||
| MM Functional |
48 |
60 |
24 |
60 |
192 |
| ABAP |
8 |
140 |
40 |
188 |
|
| TOTAL |
56 |
200 |
24 |
100 |
380 |
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]Specification
Documents
[Attach any document(s) received for the requirement(s)]Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
| Sl. |
Change Details |
Requested By |
Requested On |
Notes if any |
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]By implementing the vendor capacity planning will get the information of available vendor capacity, so that we can react to market changes without having to build up the high warehouse stocks.
In Scope:
[List the activities to be included in scope]- Implementation of standard vendor capacity planning (Including implementation of all the relevant OSS notes)
- Features/ Functions
- Vendor capacity evaluation reports
- Requisition to PO process conversion
- Configuration of vendor capacity planning
- Master data maintenance
- Creation/ change of data loading programs
- Assuming that we can go maximum up to 2 level/ node capacity structure.
Out of Scope:
[Out of scope activities]AFS Source allocation - Simulation reports and Lists
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
To implement the vendor capacity planning these are activities to be performed.
- Configuration of vendor capacity planning
- implementation of OSS note to get the correct values in the vendor capacity situation report (1289378 & 1250578)..
- Maintain the capacity for each vendor.
- Assign materials to the corresponding vendor using LSMW.
- Create a program to assign the materials to vendor capacity program.
- Assuming that we can go maximum upto 2 level/ node capacity structure. Please find below screen shot for better understanding of levels/ Nodes.
- Please find below given vendor capacity evaluation reports by Vendor, Period, Node and material.
Evaluation of Standard Vendor capacity Planning:
Vendor capacity by Vendor:
Capacity by Period:
Capacity By Node:
Capacity by Material:
Test Plan
[List test scenarios/cases to be executed here]| Test ID |
Test Scenario |
Expected Results |
| MM001 |
Maintain the capacity for one of the vendor and create standard NB POs in that period |
Value of consumed capacity should be correct |
| MM002 |
Maintain the capacity for one of the vendor and create Z3NB POs in that period |
Value of consumed capacity should be correct |
| MM003 |
Maintain the capacity for one of the vendor and create PTO POs in that period |
Value of consumed capacity should be correct |
| MM004 |
Delete the purchase order and check vendor capacity |
Consumed capacity value should be resumed in the report |
[Provide complete technical details for configuration or programming here]
Implement the vendor capacity planning after getting approval from New Era.
1. Implemented Exit - 'EXIT_SAPMM06E_012' to assign materials to Vendor Capacity Planning while saving Purchase Order.
2. Created a program ZMM_VCP_ASSIGN to assign materials to Vendor Capacity Planning for Initial Load from the Flat File
VCP - Format.txt
Issues
[List Issues / Bugs identified in configuration or development]
Issues observed during testing in Quality.
1. Observed inconsistencies in the vendor capacity simulation report.
2. Observed occasionally 'Book with new period POPUP during creation of purchase order.
3. During testing observed that number range is very less (0-999999).
After go-live observed these issues.
1. Observed frequently 'book with new period POPUP during creation purchase order.
2. Some times purchase orders are saving very slow and going for dump.
3. Correction report /AFS/J_3AMCAC taking more time like more than one day.
4. Observed inconsistencies in the vendor capacity simulation report.
5. Inconsistent data in a particular period (7th Period)
For all the above issues are escalated to SAP, Since all these issues are due to bug in the VCP program.
1. SAP has released the OSS note 2290525, 2299274 to resolve the 'book with new period POPUP' issue during creation of purchase order.
2. SAP has released the OSS note 2300157 to resolve the inconsistencies in the vendor capacity simulation report.
3. SAP has released the OSS note 2298945 to improve the performance of vendor capacity correction report.
4. SAP has released the OSS note 2308383 to increase the number range of vendor capacity.
5. SAP has released the OSS note 2317140 to remove the inconsistencies in a particular period.
6. SAP has released the OSS note 2298087 to remove the inconsistencies in when pre-packs are used.
7. SAP has released the OSS note 1289378 & 2286052 to correct the correction report /AFS/J_3AMCAC.
8. SAP has released the OSS note 2309648 to determine correct capacity period.
9. SAP has released the OSS note 2281231 to resolve the update termination issue during change of PO.
.
Go-Live Schedule (06/25/2016)
| Steps |
Process |
Date |
Tent Time |
IST |
EST |
Responsible |
| Step1 |
Vendor capacity data extraction |
6/24/2016 |
Laxman |
|||
| Step6 |
Extract materials of PO till date |
6/24/2016 |
Babu |
|||
| Step2 |
User exit deactivation |
6/25/2016 |
5mins |
11:00 |
01:30 |
Laxman |
| Step3 |
Data deletion |
6/25/2016 |
10mins |
11:05 |
01:35 |
Laxman |
| Step4 |
Move all TPs and OSS notes |
6/25/2016 |
1hr |
11:15 |
01:45 |
Laxman |
| Step5 |
Maintain vendor capacities |
6/25/2016 |
30mins |
12:15 |
02:45 |
Laxman |
| Step7 |
Assign materials one vendor |
6/25/2016 |
15mins |
12:45 |
03:15 |
Laxman |
| Lunch Break - 30 Mins |
||||||
| Step8 |
Run correction reports one vendor |
6/25/2016 |
2hr |
01:30 |
04:00 |
Laxman |
| Step9 |
Convert req into PO |
6/25/2016 |
15mins |
03:30 |
06:00 |
Babu |
| Step10 |
Assign materials to all other vendors |
6/25/2016 |
2hr |
03:45 |
06:15 |
Laxman |
| 05:45 |
08:15 |
|||||
| Step11 |
Run correction reports to all vendors |
6/25/2016 |
Report will be scheduled one after one |
Babu |
||